-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Vacated Decision Issues from Request Issues #13173
Conversation
adjusted tests accordingly;
…active atty to pass (ensure variables are created in necessary order)
…nUpdater rather than on frontend; additional fields saved in newly created request issues;
…issue_ids for full grant
…ecisionMotionUpdater
Code Climate has analyzed commit 0d24049 and detected 0 issues on this pull request. View more on Code Climate. |
…cisionMotion; moved `create_vacated_decision_issue` in RequestIssue to make method accessible;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added some thoughts and proposals below. Let me know if you have any questions.
…otion: renamed methods, and separated methods for creation of issues from those that return said issues; renamed tests;
this creates request issues & decision issues based off the specified PostDecisionMotion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm prematurely adding a few comments for when this is adapted to the new appeal stream flow, after #13325
app/models/decision_issue.rb
Outdated
@@ -160,7 +160,7 @@ def associated_request_issue | |||
end | |||
|
|||
def create_contesting_request_issue! | |||
RequestIssue.create!( | |||
RequestIssue.find_or_create_by!( | |||
decision_review: decision_review, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are now going to be added onto the new appeal stream instead of the original appeal
@@ -25,6 +25,17 @@ def return_to_lit_support | |||
render json: { tasks: ::WorkQueue::TaskSerializer.new(appeal_tasks, is_collection: true) } | |||
end | |||
|
|||
def create_issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to move creating issues to the PostDecisionMotionUpdater, when the new appeal stream is getting created
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, if their creation is automatic we don't need an endpoint for it.
Methinks it makes sense to wait until your PR (#13325) lands and then incorporate upon new stream creation.
…sues to new "vacate" appeal stream
…tionUpdater; new issues are created on the vacate stream;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey JC - it looks like there's some "clean up" from the previous iteration of the code left, but besides that, this PR is looking good, so I'll go ahead and give it the approval now.
@@ -160,8 +160,9 @@ def associated_request_issue | |||
end | |||
|
|||
def create_contesting_request_issue! | |||
RequestIssue.create!( | |||
decision_review: decision_review, | |||
vacate_appeal_stream = Appeal.find_by(stream_type: "vacate", stream_docket_number: decision_review.docket_number) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is good for now, we'll probably update it in Sandra's ticket to pass in the decision review so it can be used for De Novo's too.
@@ -65,6 +65,8 @@ | |||
expect(task.reload.status).to eq Constants.TASK_STATUSES.completed | |||
verify_vacate_stream | |||
end | |||
|
|||
it "should create decision issues on new vacate" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a stray line
expect(request_issues.size).to eq(motion.decision_issues_for_vacatur.size) | ||
|
||
decision_issues = vacate_stream.decision_issues | ||
expect(decision_issues.size).to eq(motion.decision_issues_for_vacatur.size) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Connects #13069
Description
This adds code to create vacated decision issues from given request issues